Release 10.1A: OpenEdge Deployment:
Managing 4GL Applications

Preface

This Preface contains the following sections:

Purpose
Audience
Organization
Typographical conventions
Examples of syntax descriptions
OpenEdge messages

Purpose

This book describes how to manage Progress® 4GL client applications. The first part describes the Progress 4GL client application deployment process and application administration concepts and procedures. The second part of this book describes the steps required to deploy OpenEdge® applications and the trade-offs between different deployment scenarios. It also describes components provided with OpenEdge that help you through the deployment process. The final part contains appendices which supplement the material in the first two parts.

Audience

The first part of this book is intended for Progress application administrators. The second part is intended for experienced Progress programmers preparing applications for wider distribution or resale.

Organization

Part I, 4GL and R-code Deployment and Management

Chapter 1 "Progress 4GL Client Deployment Overview"

Presents an overview of the client deployment process, and outlines the deployment and administration tasks you must perform.

Chapter 2 "Managing Client Access to Databases"

Describes how to connect and disconnect databases for Progress 4GL clients.

Chapter 3 "Maintaining Application Security"

Describes how OpenEdge implements application security, including designating security administrators and setting table and field permissions.

Chapter 4 "Maintaining User Environments"

Describes how to maintain OpenEdge user interface environments in Windows and on UNIX.

Chapter 5 "Managing Client Performance"

Describes how to monitor and tune Progress 4GL client application performance.

Chapter 6 "Managing R-code Libraries"

Describes Progress 4GL r-code libraries and how to use the PROLIB utility.

Chapter 7 "Managing Print Devices"

Describes how to set up print devices on OpenEdge-supported operating systems.

Part II, Deployment Considerations

Chapter 8 "Choosing a Code Format"

Describes the different types of code formats you can choose to deploy a Progress 4GL application.

Chapter 9 "Initial Deployment"

Describes the initial deployment process using the different code formats.

Chapter 10 "Upgrades"

Describes how to upgrade Progress 4GL applications.

Chapter 11 "Deployment Topics and Tasks"

Describes how to perform several tasks related to deploying Progress 4GL applications.

Part III, Appendices

Appendix A, "Building OpenEdge 4GL Executables"

Describes the process and requirements for building customized OpenEdge executables. It also provides instructions for using the Make utility in Windows and on UNIX.

Appendix B, "R-code Features and Functions"

Describes the structure and management of Progress r-code, the executable code into which OpenEdge compiles 4GL procedures. It also describes techniques for tuning r-code size and performance, and the use of time stamps and cyclic redundancy checks (CRCs) to maintain r-code and database integrity.

Appendix C, "OpenEdge Application Limits"

Describes the OpenEdge limits you must consider when developing an OpenEdge client application.

Appendix D, "Deployment Utilities and Scripts"

Provides reference information about utilities and scripts you can use when deploying your application.

Typographical conventions

This manual uses the following typographical conventions:

Convention	Description
Bold	Bold typeface indicates commands or characters the user types, provides emphasis, or the names of user interface elements.
Italic	Italic typeface indicates the title of a document, or signifies new terms.
SMALL, BOLD CAPITAL LETTERS	Small, bold capital letters indicate OpenEdge® key functions and generic keyboard keys; for example, GET and CTRL.
KEY1+KEY2	A plus sign between key names indicates a simultaneous key sequence: you press and hold down the first key while pressing the second key. For example, CTRL+X.
KEY1 KEY2	A space between key names indicates a sequential key sequence: you press and release the first key, then press another key. For example, ESCAPE H.
Syntax:
Fixed width	A fixed-width font is used in syntax statements, code examples, system output, and filenames.
Fixed-width italics	Fixed-width italics indicate variables in syntax statements.
Fixed-width bold	Fixed-width bold indicates variables with special emphasis.
UPPERCASE fixed width	Uppercase words are Progress® 4GL language keywords. Although these are always shown in uppercase, you can type them in either uppercase or lowercase in a procedure.
	This icon (three arrows) introduces a multi-step procedure.
	This icon (one arrow) introduces a single-step procedure.
Period (.) or colon (:)	All statements except DO, FOR, FUNCTION, PROCEDURE, and REPEAT end with a period. DO, FOR, FUNCTION, PROCEDURE, and REPEAT statements can end with either a period or a colon.
[ ]	Large brackets indicate the items within them are optional.
[ ]	Small brackets are part of the Progress 4GL language.
{ }	Large braces indicate the items within them are required. They are used to simplify complex syntax diagrams.
{ }	Small braces are part of the Progress 4GL language. For example, a called external procedure must use braces when referencing arguments passed by a calling procedure.
|	A vertical bar indicates a choice.
...	Ellipses indicate repetition: you can choose one or more of the preceding items.

Examples of syntax descriptions

In this example, ACCUM is a keyword, and aggregate and expression are variables:

Syntax

ACCUM aggregate expression

FOR is one of the statements that can end with either a period or a colon, as in this example:

FOR EACH Customer:   DISPLAY Name. END.

In this example, STREAM stream, UNLESS-HIDDEN, and NO-ERROR are optional:

Syntax

DISPLAY [ STREAM stream ] [ UNLESS-HIDDEN ] [ NO-ERROR ]

In this example, the outer (small) brackets are part of the language, and the inner (large) brackets denote an optional item:

Syntax

INITIAL [ constant [ , constant ] ]

A called external procedure must use braces when referencing compile-time arguments passed by a calling procedure, as shown in this example:

Syntax

{ &argument-name }

In this example, EACH, FIRST, and LAST are optional, but you can choose only one of them:

Syntax

PRESELECT [ EACH | FIRST | LAST ] record-phrase

In this example, you must include two expressions, and optionally you can include more. Multiple expressions are separated by commas:

Syntax

MAXIMUM ( expression , expression [ , expression ] ... )

In this example, you must specify MESSAGE and at least one expression or SKIP [ (n) ], and any number of additional expression or SKIP [ ( n ) ] is allowed:

Syntax

MESSAGE { expression | SKIP [ ( n ) ] } ...

In this example, you must specify {include-file, then optionally any number of argument or &argument-name = "argument-value", and then terminate with }:

Syntax

{ include-file     [ argument | &argument-name = "argument-value" ] ... }

Long syntax descriptions split across lines

Some syntax descriptions are too long to fit on one line. When syntax descriptions are split across multiple lines, groups of optional and groups of required items are kept together in the required order.

In this example, WITH is followed by six optional items:

Syntax

WITH [ ACCUM max-length ] [ expression DOWN ]   [ CENTERED ] [ n COLUMNS ] [ SIDE-LABELS ]   [ STREAM-IO ]

Complex syntax descriptions with both required and optional elements

Some syntax descriptions are too complex to distinguish required and optional elements by bracketing only the optional elements. For such syntax, the descriptions include both braces (for required elements) and brackets (for optional elements).

In this example, ASSIGN requires either one or more field entries or one record. Options available with field or record are grouped with braces and brackets:

Syntax

ASSIGN   { [ FRAME frame ] { field [ = expression ] }             [ WHEN expression ] } ...        | { record [ EXCEPT field ... ] }

OpenEdge messages

OpenEdge displays several types of messages to inform you of routine and unusual occurrences:

Execution messages inform you of errors encountered while OpenEdge is running a procedure; for example, if OpenEdge cannot find a record with a specified index field value.
Compile messages inform you of errors found while OpenEdge is reading and analyzing a procedure before running it; for example, if a procedure references a table name that is not defined in the database.
Startup messages inform you of unusual conditions detected while OpenEdge is getting ready to execute; for example, if you entered an invalid startup parameter.

After displaying a message, OpenEdge proceeds in one of several ways:

Continues execution, subject to the error-processing actions that you specify or that are assumed as part of the procedure. This is the most common action taken after execution messages.
Returns to the Progress Procedure Editor, so you can correct an error in a procedure. This is the usual action taken after compiler messages.
Halts processing of a procedure and returns immediately to the Progress Procedure Editor. This does not happen often.
Terminates the current session.

OpenEdge messages end with a message number in parentheses. In this example, the message number is 200:

** Unknown table name table. (200)

If you encounter an error that terminates OpenEdge, note the message number before restarting.

Obtaining more information about OpenEdge messages

In Windows platforms, use OpenEdge online help to obtain more information about OpenEdge messages. Many OpenEdge tools include the following Help menu options to provide information about messages:

Choose Help Recent Messages to display detailed descriptions of the most recent OpenEdge message and all other messages returned in the current session.
Choose Help Messages and then type the message number to display a description of a specific OpenEdge message.
In the Progress Procedure Editor, press the HELP key or F1.

On UNIX platforms, use the Progress pro command to start a single-user mode character OpenEdge client session and view a brief description of a message by providing its number.

To use the pro command to obtain a message description by message number:

Start the Progress Procedure Editor:

install-dir/dlc/bin/pro

Press F3 to access the menu bar, then choose Help Messages.
Type the message number and press ENTER. Details about that message number appear.
Press F4 to close the message, press F3 to access the Progress Procedure Editor menu, and choose File Exit.